Note

Description

This PR expands the functions command group with three new subcommands (list, delete, pull) and significantly refactors the deploy subcommand. Deployment now happens function-by-function sequentially with real-time per-function progress feedback, supports selective deployment by name, and adds a --force flag to prune remote functions not present locally. The underlying API layer was also refactored from a single batch endpoint to individual per-function endpoints.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• functions list — new command that fetches and displays all deployed functions on the remote, including automation counts
• functions delete [names...] — new command to delete one or more functions by name (supports comma-separated and variadic args); gracefully handles 404s
• functions pull [name] — new command to pull deployed function code from Base44 to local disk; skips files already matching remote content; optionally scoped to a single function by name
• functions deploy refactor — now accepts optional [names...] to deploy a subset, shows step-by-step [n/total] progress per function, and adds --force to delete remote-only functions after deploying
• Core API refactor (core/resources/function/api.ts) — replaced single-batch deployFunctions with deploySingleFunction, deleteSingleFunction, and listDeployedFunctions targeting per-function REST endpoints
• Schema updates (schema.ts) — replaced DeployFunctionsResponseSchema with DeploySingleFunctionResponseSchema, added FunctionInfoSchema and ListFunctionsResponseSchema
• Core deploy logic (core/resources/function/deploy.ts) — extracted deployFunctionsSequentially and pruneRemovedFunctions with callback hooks for live progress reporting
• New core pull module (core/resources/function/pull.ts) — writeFunctions writes remote function files locally and skips unchanged files via deep-equality checks
• Tests — added functions_delete.spec.ts, functions_list.spec.ts, functions_pull.spec.ts; updated functions_deploy.spec.ts and TestAPIServer with new mock endpoints

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

The pull command writes a function.jsonc config file plus all source files into <functionsDir>/<name>/. It compares local file contents against the remote before writing, so re-running pull on an already-synced repo produces no writes. The --force flag on deploy is mutually exclusive with specifying function names by design.

_{🤖 Generated by Claude | 2026-03-16 00:00 UTC}